Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add napping recipe #25122

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

Add napping recipe #25122

wants to merge 7 commits into from

Conversation

goanpeca
Copy link
Member

@goanpeca goanpeca commented Jan 23, 2024

Checklist

  • Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
  • License file is packaged (see here for an example).
  • Source is from official source.
  • Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
  • If static libraries are linked in, the license of the static library is packaged.
  • Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
  • Build number is 0.
  • A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
  • GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
  • When in trouble, please check our knowledge base documentation before pinging a team.

See:

@conda-forge-webservices
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/napping) and found some lint.

Here's what I've got...

For recipes/napping:

  • The following maintainers have not yet confirmed that they are willing to be listed here: jaimergp. Please ask them to comment on this PR if they are.

@goanpeca goanpeca self-assigned this Jan 23, 2024
@goanpeca
Copy link
Member Author

We are in the process of creating conda packages for napari plugins and related dependencies. Once this recipe passes all the checks, every time a new release goes into PyPI, a PR will be created automatically, with usually very minor need for changes so the process of maintaining this moving forward is small. Also the @conda-forge/napari team will be available to help as needed.

You can read a bit more about conda-forge at https://conda-forge.org/#contribute


@jaimergp, @jwindhager, do you agree with being added as maintainers?

@jwindhager
Copy link
Contributor

@jaimergp, @jwindhager, do you agree with being added as maintainers?

This project is being maintained by @Milad4849

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants